home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
AMOS PD CD
/
amospdcd.iso
/
aminet
/
amoslist0993.lzh
/
AMOSLIST2
/
000034_amos-request@svcs1.digex.net_Wed Sep 1 00:26:04 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1993-09-03
|
2KB
Received: from nextsun.INS.CWRU.Edu by access.digex.net with SMTP id AA25392
(5.65c/IDA-1.4.4 for <mcox@access.digex.com>); Wed, 1 Sep 1993 00:26:02 -0400
Received: from svcs1.digex.net by nextsun.INS.CWRU.Edu with SMTP (5.65b+ida+/CWRU-1.5.2-freenet-gw)
id AA15571; Wed, 1 Sep 93 00:24:27 -0400 (from amos-request@svcs1.digex.net for mcox@access.digex.com)
Received: by svcs1.digex.net id AA00266
(5.65c/IDA-1.4.4 for amos-list-out); Tue, 31 Aug 1993 23:37:07 -0400
Received: from access.digex.net by svcs1.digex.net with SMTP id AA00262
(5.65c/IDA-1.4.4 for <amos-list@svcs1.digex.net>); Tue, 31 Aug 1993 23:37:04 -0400
Received: from vax.mbhs.edu by access.digex.net with SMTP id AA01905
(5.65c/IDA-1.4.4 for <amos-list@access.digex.net>); Tue, 31 Aug 1993 22:13:02 -0400
Message-Id: <199309010213.AA01905@access.digex.net>
Date: 31 Aug 93 20:08:00 EST
From: "Andrew Church" <95ACHURCH@vax.mbhs.edu>
Subject: Re: Jumping/flicker
To: "amos-list" <amos-list@access.digex.net>
Status: RO
>If I remember correctly the scrolly/menu I wrote has ->
>
>Close Workbench
>Close Editor
>
>At the beginning. This should kill the shell and give control to the AMOS
>program being run. Even when this is so the scrolly still flickers every
>now and then.
If you have a Shell window open, Close Workbench will *NOT* work. This is
because the Shell is a window on the Workbench screen that is not part of
Workbench itself. Intuition cannot force "visitor" windows to close, so it
cannot close Workbench.
I've never noticed much difference between multitasking on and multitasking
off when I don't have any other programs running at the same time (excepting
Workbench and a shell). It shouldn't make that much difference, anyway.
Remember that a lot of the stuff Workbench does when you're not using it, like
checking for disks, is interrupt-driven anyway, and it's not a good idea to
turn off interrupts for a lengthy period of time.
--Andy Church